Team Focus?
Original Post
Untested idea. Might not work. Probably needs tweaking.
Picture a whiteboard with post-it notes, which represents something like an AF4 list. A typical board fits 10 down, 14 across. Imagine there's two and a half columns of post-its, then a marker-drawn horizontal line (closed list) , then 4 more columns of post-its (open list). The team
- looks at the board,
- examines items one by one, and
- each person may select something to work on by grabbing the post-it.
- When everybody has something, flag the last scanned spot.
When anybody finishes or gets stuck, they
- return to the board,
- If there's more to do, repost the card at the list-end, note the new status
- if there's no more to do, post the card in a Done area
- post new cards if new ideas come up, and then
- pick a new item starting from the flag.
If, per rules AF rules, tasks need to be dismissed,
- move these to a dismissal area where the team or manager can review them.
- Draw a new line for a new closed list.
- Wrap the list around the board when you hit the right wall.
Picture a whiteboard with post-it notes, which represents something like an AF4 list. A typical board fits 10 down, 14 across. Imagine there's two and a half columns of post-its, then a marker-drawn horizontal line (closed list) , then 4 more columns of post-its (open list). The team
- looks at the board,
- examines items one by one, and
- each person may select something to work on by grabbing the post-it.
- When everybody has something, flag the last scanned spot.
When anybody finishes or gets stuck, they
- return to the board,
- If there's more to do, repost the card at the list-end, note the new status
- if there's no more to do, post the card in a Done area
- post new cards if new ideas come up, and then
- pick a new item starting from the flag.
If, per rules AF rules, tasks need to be dismissed,
- move these to a dismissal area where the team or manager can review them.
- Draw a new line for a new closed list.
- Wrap the list around the board when you hit the right wall.
Reply by Alan Baljeu
I should explain why. I find AF provides a very important balance between big and small, important and urgent. I would like to bring that quality to team work. Kanban seems to be good for ensuring what you start gets finished, but it doesn't provide much guidance in choosing what to start, and also tends to narrow the scope of discussion to project items.
Above I posted mechanics, but I think a discussion of balancing team effort might be more pertinent. Perhaps completely different approaches are better for this context.
Ideas?
Above I posted mechanics, but I think a discussion of balancing team effort might be more pertinent. Perhaps completely different approaches are better for this context.
Ideas?
Reply by Erik
I agree that some system is needed when working in groups. I personally find that using a Kanban is the best way to approach it. It's kinda similar to what you propose in that : you use intuition, you see big and small things but since there is a "done" column, people have a sense of completion.
AF is great if you are mindful about the fact that your list will never end. The closed lists parts will but the list itself will not. It's good for a "chipping at the mountain" kind of thinking but you can't expect people to adhere to it...
AF is great if you are mindful about the fact that your list will never end. The closed lists parts will but the list itself will not. It's good for a "chipping at the mountain" kind of thinking but you can't expect people to adhere to it...
Reply by JD
Erik - but there can be subtle sense of completion with AF. Where you draw the line separating the closed and open lists, I write the date it was created. The faster I get the open list to close, the better I feel about my progress of work.
Obviously, if you cheat yourself and just "bring the file out" for every closed list task just to get to completion, it won't work, and that dang intuition-thing will shout it out to you. But that wouldn't work for any system.
That date trick is from Mark I believe, and it is a subtle progress marker in itself, I find.
Obviously, if you cheat yourself and just "bring the file out" for every closed list task just to get to completion, it won't work, and that dang intuition-thing will shout it out to you. But that wouldn't work for any system.
That date trick is from Mark I believe, and it is a subtle progress marker in itself, I find.
Reply by nuntym
+AJPM+
I agree with Erik, a Kanban system is I think the best way to do that, Alan. I think a simple picture will say it all:
http://www.personalkanban.com/pk/wp-content/uploads/2009/08/whiteboards-050.jpg
God bless.
I agree with Erik, a Kanban system is I think the best way to do that, Alan. I think a simple picture will say it all:
http://www.personalkanban.com/pk/wp-content/uploads/2009/08/whiteboards-050.jpg
God bless.
Reply by Alan Baljeu
As I said, Kanban is fine for advancing tasks to completion. We can use this for that.
My search is a way to be sure a proper variety of things are chosen to fill the board.
My search is a way to be sure a proper variety of things are chosen to fill the board.
Reply by Seraphim
The problem I have with Kanban (including the system described in Erik Lorraine's video, which had me thinking about it for two weeks!) is the sheer volume of tasks that are always on my list. I've been doing DWM since its inception and typically have 600 to 800 individual active items on my task list at any given time: individual emails, voicemails, projects, project-related tasks, recurring tasks, occasional-maintenance tasks, one-off tasks, one-off ideas to explore, etc.
I really liked Erik's kanban based ideas and tried to find a way to merge them with my workload but in the end I gave up.
For a team-based system, I think the teams I am on would have the same issue. There's just too much volume of tasks with complex interrelationships. We are also geographically dispersed, and screen-based Kanban systems I've seen don't have enough resolution to display 100+ tasks in a useful way.
(I'd love your feedback or comments on this!)
I really liked Erik's kanban based ideas and tried to find a way to merge them with my workload but in the end I gave up.
For a team-based system, I think the teams I am on would have the same issue. There's just too much volume of tasks with complex interrelationships. We are also geographically dispersed, and screen-based Kanban systems I've seen don't have enough resolution to display 100+ tasks in a useful way.
(I'd love your feedback or comments on this!)
Reply by Mark Forster
Seraphim:
That was certainly my reaction too when I looked at Kanban. I couldn't see how it could deal with the sheer volume of tasks that most individuals have, let alone teams.
That was certainly my reaction too when I looked at Kanban. I couldn't see how it could deal with the sheer volume of tasks that most individuals have, let alone teams.
Reply by Alan Baljeu
Seraphim I agree screen resolution is limited. We use a whiteboard.
We are attempting to follow a Kanban at work. To clarify some confusion:
1. It isn't tasks that go on the team board, but rather standardized items of a particular variety. In our case the items are expected software behaviours. "saving files"
The tasks are defined by a process represented by columns, applied to each work item. For example, "investigate. Define. Code. Test. Document. Ship"
so obviously team kanban doesn't cover everything, just the core functions of the team.
2. Kanban insists on limiting work in progress. A suggested ideal is that # of cards = 2x # of people. So hundreds won't come up.
Aside from this, there is a backlog of inactive items, which Kanban offers no advice on choosing, and everyone has his own way of tracking everything that doesn't fit the primary function.
I still seek a system that helps with those 2 issues.
We are attempting to follow a Kanban at work. To clarify some confusion:
1. It isn't tasks that go on the team board, but rather standardized items of a particular variety. In our case the items are expected software behaviours. "saving files"
The tasks are defined by a process represented by columns, applied to each work item. For example, "investigate. Define. Code. Test. Document. Ship"
so obviously team kanban doesn't cover everything, just the core functions of the team.
2. Kanban insists on limiting work in progress. A suggested ideal is that # of cards = 2x # of people. So hundreds won't come up.
Aside from this, there is a backlog of inactive items, which Kanban offers no advice on choosing, and everyone has his own way of tracking everything that doesn't fit the primary function.
I still seek a system that helps with those 2 issues.
Reply by Erik
Interesting, it's the first time I heard about the number of tasks being a problem to use what I describe. I can see where it would be unfeasible if you have even 100 open things in your backlog!!!
Remember though that what I proposed is not a way to follow which specific tasks you have done but rather to balance the "type" of tasks you have done in a day. The tasks themselves go on project lists or checklists... So what I move around is blocs of time that are general descriptions of generic tasks. If I go for a run one day just to try it out, I take my "exercise with bicycle" bloc and use that one instead of writing a new "one time" sticker ;)
p.s: By the way, I laugh every time I see it but my name is Lorrain (without the e).
I laugh because I have had teachers all my life getting my name wrong.
ex: Eric, Erick, Éric... Lorin, Laurin, Lorain, etc...
For that exact reason, I won't bite if you use it any way you feel appropriate ;)
Remember though that what I proposed is not a way to follow which specific tasks you have done but rather to balance the "type" of tasks you have done in a day. The tasks themselves go on project lists or checklists... So what I move around is blocs of time that are general descriptions of generic tasks. If I go for a run one day just to try it out, I take my "exercise with bicycle" bloc and use that one instead of writing a new "one time" sticker ;)
p.s: By the way, I laugh every time I see it but my name is Lorrain (without the e).
I laugh because I have had teachers all my life getting my name wrong.
ex: Eric, Erick, Éric... Lorin, Laurin, Lorain, etc...
For that exact reason, I won't bite if you use it any way you feel appropriate ;)
Reply by Seraphim
Erik - Sorry for misspelling your name. My own gets butchered all the time, so I sympathize. I've been called Saraphin, Sarapan, Surfing Man (I kid you not!), Syrup, Sarap, and Seraph (for those who just can't bring themselves to call a single individual by a plural name). :-)
And yes, your system focused on what ***kinds*** of tasks to do. That was pretty interesting, but my schedule is typically too chopped up by meetings and such, that if I am going to get my work done, I have to sacrifice some balance. Some of it just happens naturally -- a morning full of meetings naturally leads me to seek quiet time for the afternoon.
So, it wasn't so much the task-type-balancing that appealed to me -- it was more the visual "pull" of the kanban system.
Alan - Thanks for the clarification, that makes a lot of sense.
It's helpful to see that you are forced to focus on max number of tasks = 2x number of participants. The hard limit would naturally force you to choose. That's one of the things I like about DWM -- it forces you to limit your total tasks or else they will all start falling over the waterfall.
It's also helpful to see that "everyone has his own way of tracking everything that doesn't fit the primary function".
This is all very interesting because I'm trying a new twist on DWM right now where I have two "hot lists" that contain only my top, primary work and my top, primary personal tasks. These are the tasks that I "know" will make the most difference, the ones that keep pushing on me, the ones I keep resisting, the ones my manager (and at home, my wife) are always asking me about. I give each of them its own DWM list, and spend most of the day, outside of meetings, focusing on the Work Hotlist, and most of the evening and weekend, outside of family time, focusing on the Personal Hotlist. I have then been blocking out meetings with myself for handling maintenance and miscellaneous, each with its own DWM list.
At first I started panicking because I couldn't see what was on the lists I wasn't currently looking at. But I stopped panicking when I remembered that I had already blocked out time on my calendar to deal with those things. Each list has several time blocks per week on my calendar, so they won't get dropped.
This is the same way I handled all my regular meetings with other people, such as my biweekly 1:1 with my manager -- I just kept a DWM list of all the stuff I needed to discuss with him, and went through each item on the list when we met -- or at least whatever "stood out". If something never stood out, then it dropped off the list, and we never discussed it -- which was fine.
This way of handling ongoing meetings worked so well, I decided to set up meetings with myself to do the same thing. I've only been doing it a few days and I like it so far -- but then again, I like every new approach for the first few days. :-) Time will tell if this actually works for me or not.
But back to the main thread -- maybe I could work each of my hotlists in a Kanban way -- they are small enough that it might work. Interesting... Know any Kanban plugins for Microsoft tasks? :-)
And yes, your system focused on what ***kinds*** of tasks to do. That was pretty interesting, but my schedule is typically too chopped up by meetings and such, that if I am going to get my work done, I have to sacrifice some balance. Some of it just happens naturally -- a morning full of meetings naturally leads me to seek quiet time for the afternoon.
So, it wasn't so much the task-type-balancing that appealed to me -- it was more the visual "pull" of the kanban system.
Alan - Thanks for the clarification, that makes a lot of sense.
It's helpful to see that you are forced to focus on max number of tasks = 2x number of participants. The hard limit would naturally force you to choose. That's one of the things I like about DWM -- it forces you to limit your total tasks or else they will all start falling over the waterfall.
It's also helpful to see that "everyone has his own way of tracking everything that doesn't fit the primary function".
This is all very interesting because I'm trying a new twist on DWM right now where I have two "hot lists" that contain only my top, primary work and my top, primary personal tasks. These are the tasks that I "know" will make the most difference, the ones that keep pushing on me, the ones I keep resisting, the ones my manager (and at home, my wife) are always asking me about. I give each of them its own DWM list, and spend most of the day, outside of meetings, focusing on the Work Hotlist, and most of the evening and weekend, outside of family time, focusing on the Personal Hotlist. I have then been blocking out meetings with myself for handling maintenance and miscellaneous, each with its own DWM list.
At first I started panicking because I couldn't see what was on the lists I wasn't currently looking at. But I stopped panicking when I remembered that I had already blocked out time on my calendar to deal with those things. Each list has several time blocks per week on my calendar, so they won't get dropped.
This is the same way I handled all my regular meetings with other people, such as my biweekly 1:1 with my manager -- I just kept a DWM list of all the stuff I needed to discuss with him, and went through each item on the list when we met -- or at least whatever "stood out". If something never stood out, then it dropped off the list, and we never discussed it -- which was fine.
This way of handling ongoing meetings worked so well, I decided to set up meetings with myself to do the same thing. I've only been doing it a few days and I like it so far -- but then again, I like every new approach for the first few days. :-) Time will tell if this actually works for me or not.
But back to the main thread -- maybe I could work each of my hotlists in a Kanban way -- they are small enough that it might work. Interesting... Know any Kanban plugins for Microsoft tasks? :-)